Skip to content

Conversation

achingbrain
Copy link
Member

Where we know the type of content to be imported ahead of time (e.g. a Uint8Array or a stream, not both), it can be helpful to specify that type, so make FileCandidate generic to allow this.

Defaults it to the previous ImportContent value so this is non-breaking.

Where we know the type of content to be imported ahead of time
(e.g. a Uint8Array or a stream, not both), it can be helpful to
specify that type, so make `FileCandidate` generic to allow this.

Defaults it to the previous `ImportContent` value so this is
non-breaking.
@achingbrain achingbrain merged commit ac3d176 into master Jun 30, 2023
@achingbrain achingbrain deleted the fix/add-optional-file-candidate-content-type branch June 30, 2023 12:24
github-actions bot pushed a commit that referenced this pull request Jun 30, 2023
## [ipfs-unixfs-importer-v15.1.6](ipfs-unixfs-importer-v15.1.5...ipfs-unixfs-importer-v15.1.6) (2023-06-30)

### Bug Fixes

* add optional type for file candidate data ([#340](#340)) ([ac3d176](ac3d176))
@github-actions
Copy link

🎉 This PR is included in version ipfs-unixfs-importer-v15.1.6 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant